Fast-path implementation for an uplink double tagging engine

ABSTRACT

A network component for processing a packet can include a buffer configured to receive a packet in an ingress port at a network component, a first identification unit configured to identify a destination address and a network identifier from the packet received at the buffer, and a look-up table configured to be indexed by the destination address and the network identifier identified by the identification unit to obtain an outgoing port bit map. In addition, the network component can include a forwarding unit configured to forward the packet to a destination module and out of an egress port within the network component based on the outgoing port bit map.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims is a continuation application of U.S. patent application Ser. No. 10/378,937, filed Mar. 5, 2003, titled “FAST-PATH IMPLEMENTATION FOR AN UPLINK DOUBLE TAGGING ENGINE,” the disclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present invention relates to a method of and an apparatus for processing a packet based on a double tagging engine within a Virtual Private LAN Service (VPLS), a Transparent LAN Service (TLS), a Virtual Private Switched Network Service (VPSNS), or any Layer 2 Virtual Private Network (VPN). In essence, the present invention can be applied to any packet-based service provider communication network environment, such as token ring, ATM, Ethernet, Fast Ethernet, Gigabit Ethernet and 10 Gigabit Ethernet. In particular, the present invention relates to a method of and an apparatus for fast-path implementation for TLS using double tagging engine that can be implemented on a semiconductor substrate such as a silicon chip, or can be implemented on software, or a combination of hardware and software.

BACKGROUND

As the popularity and usage of networked computers grows, an increasing amount of end-users are being interconnected via wide area networks and the Internet. In particular, business entities, such as corporations, having multiple site-offices located in different parts of the world, are increasingly relying on the Internet to communicate with each other. For instance, a corporate entity having multiple site-offices located at geographically dispersed sites may look to a fast and efficient way of using the Internet to interconnect a group of private site-offices belonging to the private corporate entity together. Accordingly, there is a need to provide a fast, inexpensive and reliable system that can offer a virtual private customer-based network wherein inter-office network connections are achieved using the fast growing Internet infrastructure, especially the Internet Service Provider (ISP).

SUMMARY

One example of the present invention can include a method for processing a packet in a communications network. The method can include the steps of: receiving a packet in an ingress port at a network component, identifying a destination address and a network identifier from the packet, obtaining an outgoing port bit map based on the destination address and the network identifier of the packet, and forwarding the packet to a destination module and out of an egress port within the network component based on the outgoing port bit map.

In another example, the present invention can relate to a method for processing a packet in a communications network. The method can include the steps of receiving a packet in an ingress port at a network component, identifying a network identifier from the packet, accessing a packet tag corresponding to the packet, obtaining an outgoing port bit map based on the network identifier, and obtaining a membership port bit map based on the packet tag. In addition, the method can have the steps of generating an egress port bit map based on the outgoing port bit map and the membership port bit map, and forwarding the packet to a destination module and an egress port within the network component based on the egress port bit map.

In yet another example, the present invention can be a method for processing a packet in a communications network. The method can include the steps of receiving a packet in an ingress port at a network component, identifying a source module and a source port corresponding to the packet, obtaining a packet tag from the packet tag table based on the source module and the source port, assigning a packet tag priority based on a class of service of the packet, and obtaining an ether-type from a register. Furthermore, the steps can include appending the packet received within the buffer with the packet tag, the packet tag priority and the ether-type, and forwarding the packet appended with the packet tag, the packet tag priority and the ether-type to an egress port within the network component.

Another example of the present invention can be a method for processing a packet in a communications network. The method can have the steps of receiving a packet in an ingress port at a network component, removing a packet tag from the packet, obtaining a multicast index and a multicast type from indexing the packet tag to a look-up table, and appending the packet with the multicast index and the multicast type. Also, the method can have the steps of modifying an operational code of the packet to multicast when the multicast type is a first predetermined type, modifying the operation code of the packet to an IP multicast when the multicast type is a second predetermined type, assigning a first class of service for the packet with a packet tag priority, and forwarding the packet to a first egress port.

Another example of the present invention can be a network component for processing a packet. The network component can have a buffer configured to receive a packet in an ingress port at a network component, a first identification unit configured to identify a destination address and a network identifier from the packet received at the buffer, a look-up table configured to be indexed by the destination address and the network identifier identified by the identification unit to obtain an outgoing port bit map, and a forwarding unit configured to forward the packet to a destination module and out of an egress port within the network component based on the outgoing port bit map.

In another example, the present invention can relate to a network component for processing a packet. The network component can have a first buffer configured to receive a packet in an ingress port at a network component, a first identification unit configured to identify a network identifier from the packet received at the buffer, an accessing unit configured to access a packet tag corresponding to the packet received at the buffer, an outgoing port look-up table configured to be indexed by the network identifier identified by the identification unit to obtain an outgoing port bit map, a membership look-up table configured to be indexed by the packet tag accessed by the accessing unit to obtain a membership port bit map, a second buffer configured to store an egress port bit map based on the outgoing port bit map from the outgoing look-up table and the membership port bit map from the membership look-up table, and a forwarding unit configured to forward the packet to a destination module and an egress port within the network component based on the egress port bit map stored at the second buffer.

In yet another example, the present invention can be directed to a network component for processing a packet. The network component can have a buffer configured to receive a packet in an ingress port at a network component, an identifying unit configured to identify a source module and a source port corresponding to the packet received at the buffer, a packet tag look-up table configured to be indexed by the source module and the source port identified by the identifying unit to obtain a packet tag, and an assigning unit configured to assign a packet tag priority based on a class of service of the packet received at the buffer. In addition, the present example can have a register configured to store an ether-type, an appending unit configured to append the packet received at the buffer with the packet tag, the packet tag priority and the ether-type, and a forwarding unit configured to forward the packet appended with the packet tag, the packet tag priority and the ether-type by the appending unit, to an egress port within the network component.

In another example, the present invention can be related to a network component for processing a packet. The network component can include a buffer configured to receive a packet in an ingress port at a network component, a removing unit configured to remove a packet tag from the packet received at the buffer, a packet tag look-up table configured to be indexed by the packet tag removed from the removing unit to obtain a multicast index and a multicast type, and an appending unit configured to append the packet with the multicast index and the multicast type. Moreover, the present invention can have a modifying unit configured to modify an operational code of the packet to be multicast when the multicast type appended by the appending unit is a first predetermined type, a modifying unit configured to modify the operation code of the packet to be IP multicast when the multicast type is a second predetermined type, an assigning unit configured to assign a packet tag priority based on a first class of service of the packet received at the buffer, and a first forwarding unit configured to forward the packet to a first egress port.

Another example of the present invention can be directed to a system of processing a packet in a network component. The system can have a receiving means for receiving a packet in an ingress port at a network component, a first identifying means for identifying a destination address and a network identifier from the packet, an obtaining means for obtaining an outgoing port bit map based on the destination address and the network identifier of the packet, and a forwarding means for forwarding the packet to a destination module and out of an egress port within the network component based on the outgoing port bit map.

In yet another example, the present invention can relate to a system for processing a packet in a network component. The system can include a receiving means for receiving a packet in an ingress port at a network component, a first identifying means for identifying a network identifier from the packet, an accessing means for accessing a packet tag corresponding to the packet, a first obtaining means for obtaining an outgoing port bit map based on the network identifier, a second obtaining means for obtaining a membership port bit map based on the packet tag, a generating means for generating an egress port bit map based on the outgoing port bit map and the membership port bit map, and a forwarding means for forwarding the packet to a destination module and an egress port within the network component based on the egress port bit map.

In another example, the present invention can include a system for processing a packet in a network component. The system can have a receiving means for receiving a packet in an ingress port at a network component, an identifying means for identifying a source module and a source port corresponding to the packet, a first obtaining means for obtaining a packet tag from the packet tag table based on the source module and the source port, and an assigning means for assigning a packet tag priority based on a class of service of the packet. Furthermore, the system can have a second obtaining means for obtaining an ether-type from a register, an appending means for appending the packet received within the buffer with the packet tag, the packet tag priority and the ether-type, and a forwarding means for forwarding the packet appended with the packet tag, the packet tag priority and the ether-type to an egress port within the network component.

In another example, the present invention can include a system for processing a packet in a network component. The said system can have a first receiving means for receiving a packet in an ingress port at a network component, a removing means for removing a packet tag from the packet, a first obtaining means for obtaining a multicast index and a multicast type from indexing the packet tag to a look-up table, and an appending means for appending the packet with the multicast index and the multicast type. In addition, the system can have a first modifying means for modifying an operational code of the packet to multicast when the multicast type is a first predetermined type, a second modifying means for modifying the operation code of the packet to an IP multicast when the multicast type is a second predetermined type, an assigning means for assigning a first class of service for the packet with a packet tag priority, and a first forwarding means for forwarding the packet to a first egress port.

BRIEF DESCRIPTION OF THE DRAWINGS

For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

FIG. 1 illustrates one example of a Transparent LAN Service Network System in accordance with the present invention;

FIG. 2 illustrates another example of a Transparent LAN Service Network System in accordance with the present invention;

FIG. 3 illustrates one example of a Provider Edge Device in accordance with the present invention;

FIG. 4 illustrates another example of a Provider Edge Device in accordance with the present invention;

FIG. 5( a) illustrates one example of a packet inserted with a customer VLAN ID tag in accordance with the present invention;

FIG. 5( b) illustrates one example of a packet inserted with a customer VLAN ID tag, an SP VLAN tag, and additional information in accordance with the present invention;

FIG. 6 illustrates one example of a method of processing a packet based on double tagging engine within a TLS network system;

FIG. 7 illustrates another example of a method of processing a packet based on double tagging engine within a TLS network system;

FIG. 8 illustrates yet another example of a method of processing a packet based on double tagging engine within a TLS network system;

FIG. 9 illustrates one additional example of a method of processing a packet based on double tagging engine within a TLS network system; and

FIG. 10 illustrates another example of a method of processing a packet based on double tagging engine within a TLS network system.

DETAILED DESCRIPTION

FIG. 1 illustrates one example of a fast-path Transparent LAN Service (hereinafter “TLS”) network system 10 that can implement double tagging. The TLS network system 10 of this example can be configured to deliver Ethernet or other service to multiple customers geographically dispersed across a network, such as a Wide Area Network (WAN) or Metro Area Network (MAN), as if the multiple customers were connected through a Local Area Network (LAN).

The TLS network system 10 as shown in FIG. 1 illustrates a Service Provider Network (SPN) 20. The SPN 20 can be a packet switched network, such as the Internet. Also, FIG. 1 shows a plurality of Provider Edge (PE) devices PE 1, PE 2, PE 3 . . . PE n connected to the SPN 20.

In addition, FIG. 1 illustrates TLS network system 10 having two VPLS customers, VPLS CUST A and VPLS CUST B. It is noted that although FIG. 1 shows a TLS network system 10 having two VPLS customers, the present invention can be configured to handle a plurality of VPLS customers CUST n within the TLS network system 10.

Each VPLS CUST A and B can be connected to a PE device. In addition, each VPLS customer can have its own plurality of independent Virtual Local Area Networks (VLAN), VLAN 1, VLAN 2 . . . VLAN n. Accordingly, FIG. 1 shows VLAN 1, VLAN 2 . . . VLAN n of VPLS CUST A being “bridged” transparently over SPN 10, wherein a Service Provider VLAN, SP VLAN 30, can be configured to specifically carry all of VPLS CUST A's communication traffic. Similarly, FIG. 1 shows VLAN 1, VLAN 2 . . . VLAN n of VPLS CUST B being “bridged” transparently over SPN 10, wherein SP VLAN 40 can be configured to carry all of VPLS CUST B's communication traffic.

FIG. 2 illustrates another example of a TLS network system 15 that can include a SPN 25 and PE devices PE 1 and PE 2. Each PE device can be configured to have a plurality of ports, such as at least one uplink port, upt 1 and one or more customer facing port(s), pt 0, pt 1 . . . pt n. Each port within each of the PE devices can be configured to be a receiving port, or an ingress port, as well as a transmitting port, or an egress port, for receiving and transmitting a packet, respectively. Although the TLS network system 10, 15 of the present example can manage data and/or information in the form of a packet, it is noted that in other examples of the present invention, the TLS network system 10, 15 can be configured to also manage data and/or information in other formats, such as a data frame, or a data cell. Therefore, any reference to a packet herein can also refer to at least a frame, a cell, or a data packet, a data frame or a data cell.

Further shown in FIG. 2, each port within the PE devices can be organized into groups of port(s) for one or more customer(s), wherein each organized group of port(s) can represent a VPLS domain for the TLS network system 15. According to FIG. 2, a specific customer can be provided with one or more port(s) from the PE device. As such, each port from within the organized group of port(s) assigned to the specific customer can be designated to connect with each and every VLAN of that particular customer, or selected VLANs. It is noted that one or more customer(s) can share the same organized group of port(s) from the PE device if each customer share the same set of unique VLAN IDs.

For instance, FIG. 2 shows PE devices PE 1 and PE 2 connected to a SPN 25 via an uplink port upt1, wherein PE 1 and PE 2 can be two geographically dispersed sites. PE 1 and PE 2, each has a plurality of ports pt 0, pt. 1, pt 2, pt 3 . . . pt n therein. Port pt 0 of PE 1 is designated for VPLS CUST A only. Port pt 1 of the same PE device however is designed for two customers, them being VPLS CUST B and C. Furthermore, ports pt 3, pt 4, pt 5, pt 6, pt 7 and pt 8, are organized as a group of ports for VPLS CUST D. As for PE 2, port pt 4 is designated for VPLS CUST A and port pt 5 is designated to both VPLS CUST B and C. Also, ports pt n−3, pt n−2, pt n−1 and pt n, are organized as a group of ports for VPLS CUST D.

FIG. 3 illustrates one example of a hardware configuration of a PE device. The hardware configuration of FIG. 3 can be in an integrated, modular and single chip solution, and therefore can be embodied on a semiconductor substrate, such as silicon. Alternatively, the hardware configuration of FIG. 3 can be embodied in a plurality of discrete components on a circuit board.

FIG. 3 shows a PE device that can include a double tagging engine module 300, a network module A 305, a switch fabric module 310, a network module B 315, and a network module C 320. The double tagging engine module 300 can have an uplink port uplink pt 325 that can be a network port for connecting to the Ethernet, such as the Internet. In addition, the double tagging engine module 300 can include a switch fabric port SF port a 330 for connecting to the switch fabric module 310.

The PE device of FIG. 3 also shows a network module A 305, network module B 315, and network module C 320. Each of the network modules A, B and C can be a network switching chip made commercially available through Broadcom® Corporation. Additionally, each of the network modules A, B and C can have one or more customer facing ports, and one switch fabric port. The customer facing ports can connect the PE device to the customers or subscribers of the SPN. The SF ports a, b and c can connect each module to the switch fabric module 310. The customer facing ports and the SF ports a, b and c can be an ingress port as well as an egress port.

The switch fabric module 310 can also be a network switching chip made commercially available through Broadcom® Corporation.

FIG. 4 illustrates one example of a hardware configuration of a PE device 400. The hardware configuration of FIG. 4 can be in an integrated, modular and single chip solution, and therefore can be embodied on a semiconductor substrate, such as silicon. Alternatively, the hardware configuration of FIG. 4 can be embodied in a plurality of discrete components on a circuit board.

The PE device 400 can be configured to include at least one uplink port uplink pt 401, and a plurality of customer facing ports or subscriber ports, pt 0, pt 1, . . . pt n. As mentioned above, each port within the PE device can be configured to be a receiving port, or an ingress port, as well as a transmitting port, or an egress port, for receiving and transmitting a packet, respectively.

FIG. 5( a) illustrates one example of a packet 500 that can be received in or transmitted out of any one of the customer facing ports or subscriber ports pt 0, pt 1, . . . pt n. The packet 500 can be configured to include, at least a destination address field DA, a source address field SA, a customer VLAN identification tag VLAN ID, a type or length field T/L, and a payload P.

The destination address field can be a bit value that can be used by the receiving Media Access Controller (MAC), in order to determine if the incoming packet is addressed to the particular port. There can typically be three types of destination addresses i) unicast/individual or physical DA, ii) multicast or logical DA and iii) broadcast DA. The source address field can be a bit value and can be supplied by the transmitting MAC, which can insert its own unique address into the source address field as the frame is transmitted, indicating it was the original station. The receiving MAC is not required to take action based on the source address field. Furthermore, the customer VLAN ID tag is a first packet tag inserted within the packet. The VLAN ID tag can identify a particular VLAN for a unique customer. In other words, if a customer has a plurality of VLANs, such as VLAN 1, VLAN . . . VLANn, the customer VLAN ID tag can identify the packet as originating from one of the customer's VLANs. The T/L field can provide the type or the length of the packet. The payload P can contain the actual frame data that is being transferred.

FIG. 5( b) illustrates one example of a packet 510 that can be received in or transmitted out of the uplink pt 401. The packet 510 can be configured to include, at least a destination address field DA, a source address field SA, an SP VLAN tag, a customer VLAN identification tag VLAN ID, an Ether-type, a SP VLAN tag priority, an op-code and a payload P.

Packet 510 can include an SP VLAN ID tag, which can be a second tag in the packet 510. The SP VLAN ID tag can specify or identify a customer within the TLS network system 10. In other words, if a TLS network system 10 includes a plurality of customers, such as VPLS CUST A, VPLS CUST B, VPLS CUST C, and VPLS CUST D, the SP VLAN ID tag can identify the packet as originating from and belonging to a particular VPLS customer.

Therefore, packet 510 can include at least a first tag, that being a customer VLAN ID tag, and a second tag, that being a SP VLAN ID tag. The SP VLAN ID tag can identify the packet as belonging to a particular VPLS customer, and the VLAN ID tag can identify the particular VLAN belonging to that VPLS customer. Accordingly, a packet having a first and second tag can always be identified as belonging to a unique VPLS customer, even if a plurality of the VPLS customers have overlapping or common VLAN IDs.

FIG. 4 can include a storage unit 402, such as a register. The storage unit 402 can be configured to store a one-bit DT engine bit 403. The DT engine bit 403 can either be set or not set by preprogramming. For example, the DT engine bit 403 can have either the value of “1” which sets the DT engine bit 403, or the value of “0” which un-set the DT engine bit 403. When the DT engine bit 403 is set, then the PE device 400 can be operating under tagging engine mode. For instance, a bit value of “1” can indicate that the PE device 400 is operating under double tagging engine mode, and whereby a bit value of “0” can indicate that the PE device 400 is not operating under double tagging engine mode.

Furthermore, the PE device 400 of FIG. 4 can be configured to include a plurality of look-up tables, such as an SP VLAN ID tag look-up table 404, a VPLS look-up table 408, a VLAN look-up table 416, an L2 multicast look-up table 420, and an L2 address look-up table 424.

The SP VLAN ID tag look-up table 404 can include one or more SP VLAN ID tag(s) 406 therein and can be indexed by a source module and a source port from a packet. The SP VLAN ID tag(s) 406 within the table 404 can be obtained when a packet received at the PE device 400 is to be forwarded to the uplink port 401, wherein the packet is to be double tagged.

The VPLS look-up table 408 can have one or more entries therein. The VLPS look-up table 408 can be indexed by a SP VLAN ID tag so that one or more entries therein may be accessed or identified. Each mask entry can be configured to have a VPLS port bit map 410 or a membership port bit map therein. The VPLS port bit map 410 can be a bit string having a bit length that can be equal, for example, to a number of ports with the PE device 400. Each bit position of the VPLS port bit map 410 can correspond to a particular port within the PE device 400. In essence, the VPLS port bit map 410 can be configured to identify a group of one or more port(s) that correspond or belong to a particular VPLS membership for a PE device. In other words, the VPLS port bit map 410 can identify a group of one or more port(s) to which an unique customer's VLAN(s) can be mapped. Accordingly, each bit position of the VPLS port bit map 410 can be set with a value or condition of either “1” or “0”. By setting a bit position within the VPLS port bit map 410 with a value or condition of “1”, the port corresponding to the bit position can be included as part of the group of port(s) associated with the VPLS membership. In the alternative, by setting a bit position within the VPLS port bit map 410 with a value or condition of “0”, the port corresponding to the bit position can be excluded from the group of port(s) associated with the VPLS membership.

In addition, each entry within the VPLS look-up table 408 can include a Layer 2 multicast index 412 and a VPLS type 414. The Layer 2 multicast index 412 and the VPLS type 414 can correspond to a VPLS port bit map 410.

FIG. 4 also shows a VLAN ID look up table 416 within the PE device 400. The VLAN ID look-up table 416 can include one or more preprogrammed mask entries therein. Each mask entry can be configured to be an outgoing port bit map 418. The outgoing bit map 418 can be a bit string having any bit length. Each bit position of the outgoing bit map 418 can correspond to a particular port of a particular module within the PE device 400 for a particular VLAN ID. In essence, the outgoing bit map 418 can be configured to identify one or more outgoing port(s) with respect to a particular VLAN ID. Accordingly, each bit position of the outgoing bit map 418 can be set with a value or condition of either “1” or “0”. By setting a bit position within the outgoing bit map 418 with a value or condition of “1”, the port of a specified module corresponding to the bit position can be identified or specified as an outgoing port associated with a particular customer VLAN ID. In the alternative, by setting a bit position within the outgoing bit map 418 with a value or condition of “0”, the port of a specified module corresponding to the bit position can be identified or specified as not being included as an outgoing port of a particular customer VLAN ID.

The VLAN ID look-up table 416 can be indexed by the VLAN ID tag from the packet 500 of FIG. 5( a) as an example. Upon receiving the packet in an ingress port, the VLAN ID can be identified and indexed into the VLAN ID look-up table 416, wherein one VLAN ID mask entry having an outgoing port bit map 418 can be identified.

FIG. 4 also shows an L2 Multicast look-up table 420 within the PE device 400. The L2 Multicast look-up table 420 can include one or more preprogrammed mask entries therein, and the size of the L2 Multicast lookup table 420 can equal to the number of multicast groups supported by the PE device 400. In addition, each mask entry within the L2 Multicast look-up table 420 can be accessed or identified by using the customer VLAN ID and the multicast DA within the packet received. Each entry can contain a list of ports which map to a L2 multicast group.

Each mask entry within the L2 Multicast look-up table 420 can be configured to be an outgoing port bit map 422 which can be a list of ports which maps to an L2 Multicast group. The L2 Multicast look-up table 420 can be used to flood multicast packets to only those ports which have memberships of the L2 multicast group. In other words, rather than flooding a packet to the entire group of ports belonging to a particular VLAN ID, each outgoing port bit map 422 within the L2 Multicast table can be used to flood a packet to only the ports having membership of the L2 multicast group.

The outgoing port bit map 422 within the L2 Multicast look-up table 420 can be a bit string having any bit length. Each bit position of the outgoing port bit map 422 can correspond to a particular port within the PE device 400 having an L2 multicast membership. In essence, the outgoing port bit map 422 can be configured to identify one or more outgoing port(s) with respect to a particular L2 multicast group. Accordingly, each bit position of the outgoing port bit map 422 can be set with a value or condition of either “1” or “0”. By setting a bit position within the outgoing port bit map 422 with a value or condition of “1”, the port corresponding to the bit position can be identified or specified as an outgoing port associated with a particular L2 multicast membership with respect to the packet received. In the alternative, by setting a bit position within the outgoing port bit map 422 with a value or condition of “0”, the port corresponding to the bit position can be identified or specified as not being included as an outgoing port of a particular L2 multicast group with respect to the packet received.

Furthermore, FIG. 4 shows an L2 Address look-up table 424 within the PE device 400. The L2 Address look-up table 424 can include one or more preprogrammed mask entries therein. In addition, each mask entry within the L2 Address look-up table 424 can be accessed or identified by indexing the customer VLAN ID and the DA within the packet received.

Each mask entry within the L2 Address look-up table 424 can be configured to be an outgoing port bit map 426. The outgoing port bit map 426 within the L2 Address look-up table 424 can be a bit string having any bit length. Each bit position of the outgoing port bit map 426 can correspond to a port within the PE device 400. In essence, the outgoing port bit map 426 can be configured to identify one or more outgoing port(s) with respect to a packet received. Similar to above, each bit position of the outgoing bit map 426 can be set with a value or condition of either “1” or “0”. By setting a bit position within the outgoing bit map 426 with a value or condition of “1”, the port corresponding to the bit position can be identified or specified as an outgoing port with respect to the packet received. In the alternative, by setting a bit position within the outgoing bit map 426 with a value or condition of “0”, the port corresponding to the bit position can be identified or specified as not being an outgoing port with respect to the packet received.

The PE device of FIG. 3 can also include a CPU 428. The CPU 428 can be configured to implement a plurality of tasks and operations.

In addition, the PE device 400 of FIG. 4 can include an Ether-type configuration register 430. The Ether-type configuration register 430 can be configured to store an Ether-type value and can be accessed and inserted into a packet transmitted from an uplink port. Also, the PE device 400 can have one or more class of service select register(s) 434 for storing a class of service type. The class of service select register(s) 434 can correspond to a customer port.

FIGS. 6-10 illustrate one or more examples of a method of processing and double tagging a packet based on a double tagging engine thereof in accordance with the present invention. The method of the present example can be implemented in hardware, or software, or a combination of both hardware and software.

FIG. 6 shows one example of a method of processing a packet received on an Ethernet access port of a module based on a double tagging engine. A known Layer 2 unicast or a known Layer 2 multicast packet can be received at a customer subscriber port at step 600. A known unicast packet can be a packet that is relayed or transmitted to only one known destination port. In contrast, a known multicast packet can be a packet that is relayed or transmitted to multiple known destination ports. Moreover, an unknown unicast/multicast/broadcast packet can be a destination-lookup-failure packet. In other words, a received packet can be an unknown unicast/multicast/broadcast packet due to a failure in the destination address (DA) lookup for the packet received. Therefore, if the destination address lookup is not successful, then the destination port or ports with respect to the packet received is unknown.

Therefore, a known unicast or a known multicast packet can be received at one of the customer facing ports of a PE device. Once the packet is received, a destination address and a customer VLAN ID can be identified from the packet at step 605.

After identifying the destination address and the customer VLAN ID from the packet, an outgoing port bit map can be obtained from a look-up table at step 610. If the packet received is a known unicast packet, then the outgoing port bit map can be obtained from an L2 Address look-up table. However, if the packet received is a known multicast packet, then the outgoing port bit map can be obtained from an L2 Multicast look-up table.

Once the outgoing port bit map is obtained, a fast filtering processor can assign a class of service (CoS) to the module header of the packet based on a service level agreement (SLA) at step 615. Thereafter, the packet can be forwarded to one or more destination module(s) and one or more egress port(s) based on the outgoing port bit map at step 620.

FIG. 7 shows one example of a method of processing a packet received on an Ethernet access port of a DT engine module based on a double tagging engine. A known Layer 2 unicast, known Layer 2 multicast, or an unknown Layer 2 unicast, multicast or broadcast packet can be received at an Ethernet access port of a DT engine module at step 700. Once the packet is received at the Ethernet access port of the DT engine module, a source module and a source port corresponding to the packet is identified at step 705. In other words, the source module and the source port indicate the source where the packet originated therefrom.

Thereafter, the source module and the source port can be indexed to a SP VLAN tag look-up table to obtain a SP VLAN tag, which corresponds to the source module and the source port at step 710. Once the SP VLAN tag is obtained from the SP VLAN tag look-up table, a SP VLAN tag priority can be assigned to the packet based on the CoS of the packet at step 715. Additionally, an Ether-type value can be obtained from an Ether-type configuration register at step 720.

After obtaining the SP VLAN tag, and an Ether-type value, and assigning a SP VLAN tag priority, the packet received can be appended with the above information at step 725. In other words, the packet received at the Ethernet access port of a DT engine module can be appended with a SP VLAN tag, a SP VLAN tag priority and a Ether-type value therein. Once the packet is appended with such information, the packet can be forwarded out of the uplink port of the DT engine module to a SPN at step 730.

FIG. 8 shows one example of a method of processing a packet received on an Ethernet access port of a module based on a double tagging engine. An unknown Layer 2 unicast, multicast and broadcast packet can be received at subscriber port or a customer facing port of one or more network switching module such as Draco, or Tucana at step 800. Once the packet is received, a customer VLAN ID can be identified from the packet at step 805. In addition, a SP VLAN ID tag, can be identified from the packet at step 810.

After the VLAN ID and the SP VLAN ID tag have been identified from the packet, the VLAN ID can be indexed to a VLAN ID look-up table and the SP VLAN ID tag can similarly be indexed to a SP VLAN ID look-up table. Thus, an outgoing port bit map can be obtained from indexing the VLAN ID to the VLAN ID look-up table at step 815, and a VPLS port bit map or a membership port bit map can also be obtained from indexing the SP VLAN ID tag to the SP VLAN ID look-up table.

Once the outgoing port bit map and the VPLS port bit map are obtained, a logical AND operation can be performed on the two port bit maps to generate an egress port bit map at step 825. Thereafter, a CoS can be assigned to the packet based on a SLA at step 830, and the packet can be forwarded to one or more destination module(s) and an egress port based on the egress port bit map at step 835.

FIG. 9 shows one example of a method of processing a packet received on an uplink port or HiGig ingress port of a DT engine module based on a double tagging engine. A Layer 2 known unicast or a layer 2 known multicast packet can be received at the uplink port of a DT engine module at step 900. Once the packet is received, a destination address and a customer VLAN ID can be identified from the packet at step 905.

After identifying the destination address and the customer VLAN ID from the packet, an outgoing port bit map can be obtained from a look-up table at step 910. If the packet received is a known unicast packet, then the outgoing port bit map can be obtained from an L2 Address look-up table. However, if the packet received is a known multicast packet, then the outgoing port bit map can be obtained from an L2 Multicast look-up table.

Once the outgoing port bit map is obtained, a SP VLAN ID tag can be identified and removed from the packet at step 915. Thereafter, the packet can be forwarded to one or more destination module(s) and one or more egress port(s) based on the outgoing port bit map at step 920. The packet can be assigned a SP VLAN tag priority to the CoS at step 925, and the CoS SEL register can be modified on the subscriber egress port(s) to match the CoS of the packet at step 930.

FIG. 10 shows one example of a method of processing a packet received on an uplink port or high Gigabit ingress port of a DT engine module based on a double tagging engine. A Layer 2 unknown unicast, broadcast, and multicast packet can be received at an ingress uplink port of a DT engine module at step 1000. Upon receiving the packet, a SP VLAN ID tag can be identified and removed from the packet at step 1005.

The identified SP VLAN ID tag can be indexed to a Layer 2 multicast look-up table and obtain a L2 multicast index and a L2 multicast type from the look-up table at step 1010. The packet can be appended with the L2 multicast index and the L2 multicast type at step 1015. Once the packet is appended with the multicast index and the multicast type, the operation code (op-code) within the module header of the packet can be modified to “multicast” when the multicast type appended within the packet matches a first predetermined type value at step 1020. Additionally, the operation code (op-code) within the module header of the packet can be modified to “IP multicast” when the multicast type appended within the packet matches a second predetermined type value also at step 1020.

Once the packet is appended with the multicast index and type, and the op-code within the module header of the packet is modified, a SP VLAN ID priority can be assigned to the packet's CoS at step 1025. Thereafter, the packet can be forwarded to a high Gigabit ingress port of a network switching module within a PE device at step 1030.

The packet can be received at the high Gigabit port of a module with a PE device at step 1035. Once the packet is received, an outgoing port bit map can be obtained from indexing the L2 multicast look-up table at step 1040. After the outgoing port bit map is obtained, the CoS SEL register can be modified on the subscriber egress port(s) to match the CoS of the packet at step 1045, and thereafter the packet can be forwarded out of one or more subscriber customer facing port(s) based on the outgoing port bit map at step 1050.

The above-disclosed system configurations of the present invention can be embodied within a Virtual Private LAN Service (VPLS), a Transparent LAN Service (TLS), a Virtual Private Switched Network Service (VPSNS), or any Layer 2 Virtual Private Network (VPN). In addition, the above-disclosed hardware configuration can be embodied in a semiconductor substrate, such as silicon. Furthermore, the methods of the invention can be implemented in hardware, or software, or a combination of both hardware and software. In addition, a person of skill in the art with respect to network system design and/or semiconductor design and manufacturing would be able to implement the various network systems, elements and methods of the present invention onto a single system or onto a single semiconductor substrate, respectively, based upon the architectural description discussed above.

One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims. 

1. A system for processing a packet in a network component, said system comprising: a first receiving means for receiving a packet in an ingress port at a network component; a removing means for removing a packet tag from the packet; a first obtaining means for obtaining a multicast index and a multicast type from indexing the packet tag to a look-up table; an appending means for appending the packet with the multicast index and the multicast type; a first modifying means for modifying an operation code of the packet to multicast when the multicast type is a first predetermined type; a second modifying means for modifying the operation code of the packet to an IP multicast when the multicast is a second predetermined type; an assigning means for assigning a first class of service for the packet with a packet tag priority; and a first forwarding means for forwarding the packet to a first egress port. 